# Migrate ME Runtime 3.20 and earlier accounts

Opening an application that was created with an earlier version of View Studio will convert the application to the current version. Once the application has been converted, it cannot be opened by earlier versions of View Studio.

However, there is still the option of creating runtime application files that will run on earlier versions of ME Station. For this reason, it is still possible to create 3.20 and earlier users in FactoryTalk View Studio. Also, if an application that was created with an earlier version of View Studio, or an application created for PanelView Plus terminals, is imported, any users created in those applications will appear on the ME Runtime 3.20 and earlier tab of the Runtime Security editor.

If the application is intended to create run-time (.mer) files to run on earlier versions of ME Station, these users can remain on the ME Runtime 3.20 and earlier tab. However, if the application is intended for 4.00 or later, the users will need to be migrated to the ME Runtime 4.00 and later tab.

Tip: | If your system uses FactoryTalk Security, the user requesting the migration of 3.20 and earlier accounts must have Common/Write and Common/Create Children permission in the Users and Users Groups folders, and permission to modify applications in the directory. Runtime 3.20 and earlier accounts must be saved before migrating to 4.00 and later. If new users on the ME Runtime 3.20 and earlier tab have not been saved, an error message will appear when you attempt to migrate the accounts to 4.00 and later.

## To migrate ME Runtime 3.20 and earlier user accounts

1. With the Runtime Security editor open, click the View menu.
2. Select Migrate ME Runtime 3.20 and earlier accounts.

The user names on the ME Runtime 3.20 and earlier tab will appear on the ME Runtime 4.00 and later tab.

## Migrate user accounts

The following behavior applies to both private and Windows domain accounts.

- If the same user account appears on both tabs, but the security code settings and/or login/logout are different, the account on the ME Runtime 4.00 and later tab will not be changed.
- If an ME Runtime 3.20 and earlier account is not in the ME Runtime 4.00 and later account or the FactoryTalk directory, it will be added to ME Runtime 4.00 and later, and to FactoryTalk, with its 3.20 or earlier password, security codes, and login/logout macros.
- If an ME Runtime 3.20 and earlier account already exists in FactoryTalk, and has the same password in both 3.20 or earlier and FactoryTalk, it will be added to the ME Runtime 4.00 and later tab. If the password for the 3.20 account and the FactoryTalk are different, a message appears asking whether you want to replace the FT user account with the 3.x user account. To migrate the account, choose Yes.

  Tip: | ME Runtime 3.20 and earlier passwords are not case sensitive. FactoryTalk Security passwords are case sensitive. When ME Runtime 3.20 and earlier passwords are migrated, the resulting ME Runtime 4.00 and later passwords are lower case.

- If the password for a 3.20 and earlier account is shorter than the FactoryTalk policy setting for minimum password length, the account will not be migrated. (By default, the policy setting for FactoryTalk View Machine Edition is disabled, that is, set to 0 characters.)
- An information message is logged to FactoryTalk Diagnostics for each account migrated. An error message is logged for each account that cannot be migrated.
- If an ME Runtime 3.20 and earlier user account has no security codes defined, the account will initially be migrated to the ME Runtime 4.00 and later tab. However, once the Runtime Security editor has been closed and reopened, the user will not appear. This is because users who are assigned no security codes in ME Runtime 4.00 and later are not saved into the editor.

  Tip: | Do not attempt to copy and paste accounts from one tab to the other. It may produce undesirable results. If the DEFAULT user has a Login or Logout macro assigned, the macro will not be migrated with the user accounts. The security codes for the DEFAULT user are not migrated with the user accounts. If any code or event in the application (such as animation) relies on the DEFAULT user having or not having a particular code, the DEFAULT user's security code settings will have to be re-set manually to make the application work as it did in 3.20 and earlier. Be sure the DEFAULT user is allowed at least one security code that is also assigned to the initial graphic display. If the DEFAULT user has no security codes allowed, when the application is run, no display will open.

## See also

Add users or groups to FactoryTalk Security

Set up RSView 4.0 user accounts